-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix how we store Musician Groups #90
Fix how we store Musician Groups #90
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
updatedAt DateTime @updatedAt | ||
} | ||
|
||
model MusicianGroupMember { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would we need to update this data on creation/update of its user (in case the wrong data is inputted), or is this more of a one time use data for registration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's the former, where we want to display updated data in the admin dashboard so that the admin can view the updated information for group members, we may need to make a table to associate MusicianGroupMember with User.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Description
Fixes the schema to remove "group invites" and store group members differently
Motivation and Context
Closes #37
Type of changes
Checklist:
How has this been tested?
Screenshots (if appropriate):